This document describes how the hand terminal user license count in E-WMS, as per release 412.
From product update 412, E-WMS ASP will validate the hand terminal user count in your Exact Globe Next license.
This system was initially introduced in release 407, but has been redesigned in release 412.
The license validation is based on the number of active concurrent sessions and is applied when starting a specific menu on the scanner (not yet when logging in, in WMSclient).
Also, logging on using the same user name on more than one device at the same time is not allowed, since E-WMS cannot support this way of working.
This license validation recognizes following hand terminal license modules:
This license validation is done after selecting a specific scan function (menu), and not immediately after logging on on a scanner. Only then, E-WMS can determine what license would apply for the started function. Following license modules are validated per ASP menu:
When starting a scanner menu and exceeding the user limit for that module, following message will show:
"The current number of active scanners exceeds your license. Please contact customer support if you want to purchase additional license. (SE1385)."
The license code shown in this message depends on what menu was started, and indicates what license module should be purchased if additional licenses are required.
User name validation
When logging in, it is possible there is already a session active with the same user name. This can be the case because of two reasons:
When logging on with a username already used in another active session, then after selecting any scanning menu, the user in the first session will see this message as soon he continues any action: The user who logged in the second session, is able to start or continue his scanning process. This is necessary because of above mentioned scenario 1.
There is only one exception where the second session cannot take over the first session: when the first session was still waiting for a server action. This could be the case when using E-WMS Autoreceive, and when generating numbers or labels. In that case the session is waiting for the server to complete its action, and the user in session 2 cannot log on (the same message as above will be shown) until that server action is completed. As for 'timing'; it is not likely that a second logon will occur just when session 1 is waiting for a server action.
When a WMSclient session ends unexpectedly, a time-out will automatically be applied, after which the still active IIS session is automatically closed. This session time-out is configured (default 15 minutes) in the IIS file web.config for the E-WMS web site. This time-out will only occur for sessions which are no longer active.